Skip to main content

Web Accessibility

What you need to know

All web content published on Loyola public websites must be accessible to everyone, including people who use screen readers, keyboard navigation, or other assistive technologies. 

Accessibility applies to:

  • web pages.
  • PDFs.
  • images.
  • videos.
  • forms.

As a web editor, your role is to ensure the content you publish meets accessibility standards. If you're unsure, the UMC Digital Team can help.

Your responsibility as a Site Content Coordinator

You do not need to memorize accessibility law or technical standards. But, you do need to:

  • add alternative text to images.
  • use descriptive link names.
  • structure content with proper headings.
  • ensure tables include headers.
  • avoid uploading inaccessible PDFs.

These small decisions have a significant impact on usability.

Quick Accessibility Fixes for Web Content Editors

Images

All meaningful images must include alternative text ("alt text"). Alt text should:

  • Describe what is happening in the image.
  • Be concise (1-3 sentences).
  • Not begin with "image of" or "picture of."

When uploading an image into the Terminalfour (T4) Media Library, always fill in the alt text in addition to filling out the alt text field within the page content type itself (when available).

Image Alt Text Video Tutorial

Link names

Links must describe their destination. Avoid generic phrases:

  • "Click here"
  • "Read more"
  • "Link"

Instead, use specific language:

  • "Download the Finance PDF"
  • "View the Academic Calendar"
  • "Contact the Office of Admission"

If you saw the link language out of context, would you know where it goes? If not, rewrite it.

Page titles

Page titles appear in the tab of your browser. Each page must have a unique, descriptive title. The page title should:

  • reflect the content of the page.
  • match or closely align with the main heading.
  • not be generic (e.g. "home" or "untitled").

In Terminalfour, add this in the "Meta Title" field under the "General" tab and save the page. 

Page Title Video Tutorial

Tables

Tables must include header rows (and header columns when appropriate). Without headers, assistive technology cannot interpret the structure of the table. Use tables only for data, not for layout.

Column 1 Column 2
table data table date
example example
Column 1 Column 2 Column 3
Row 1 table data table data
Row 2 example example

Headings

Headings create structure and help users navigate. Follow this hierarchy:

  • One Level 1 heading per page
  • Level 2 headings for main sections
  • Level 3 headings for sub-sections

Do not change text size or bold text to simulate a heading. Use the proper heading styles in T4.

When to ask for help

You should contact the UMC Digital Team if:

  • you are unsure how to structure complex content.
  • your page is flagged repeatedly for accessibility issues.
  • you are uploading a PDF.
  • you receive accessibility-related feedback.

Accessibility is a shared responsibility. Asking early prevents rework later.

If you would like a detailed accessibility report from our Siteimprove platform to identify specific areas for improvement, please submit a request.

Why accessibility matters

Loyola is working to meet updated ADA Title III web accessibility requirements, which adopt WCAG 2.1 Level AA standards. This means all web content must meet established accessibility criteria. Accessibility ensures:

  • everyone can access important information.
  • Loyola meets legal and ethical obligations.
  • content is usable across devices and technologies.

What is WCAG?

The Web Content Accessibility Guidelines (WCAG) are internationally recognized standards for digital accessibility. WCAG is based on four principles:

  • Perceivable Content can be seen or heard
  • Operable Users can navigate and interact
  • Understandable Content is clear and predictable
  • Robust Works with assistive technologies

You are not expected to memorize WCAG criteria. UMC Digital monitors and supports compliance at the system level.

Additional Resources

Report an Issue

Notice an accessibility issue? Submit a request and our team will review it.

Submit a web request

Learn about PDF remediation

Understand how PDFs are evaluated for accessibility and what options are available.

Learn more about PDFs

Contact UMC Digital

Questions about accessibility, PDFs, or web standards? Contact UMC Digital for support.

Contact UMC Digital

What you need to know

All web content published on Loyola public websites must be accessible to everyone, including people who use screen readers, keyboard navigation, or other assistive technologies. 

Accessibility applies to:

  • web pages.
  • PDFs.
  • images.
  • videos.
  • forms.

As a web editor, your role is to ensure the content you publish meets accessibility standards. If you're unsure, the UMC Digital Team can help.

Your responsibility as a Site Content Coordinator

You do not need to memorize accessibility law or technical standards. But, you do need to:

  • add alternative text to images.
  • use descriptive link names.
  • structure content with proper headings.
  • ensure tables include headers.
  • avoid uploading inaccessible PDFs.

These small decisions have a significant impact on usability.

Quick Accessibility Fixes for Web Content Editors

Images

All meaningful images must include alternative text ("alt text"). Alt text should:

  • Describe what is happening in the image.
  • Be concise (1-3 sentences).
  • Not begin with "image of" or "picture of."

When uploading an image into the Terminalfour (T4) Media Library, always fill in the alt text in addition to filling out the alt text field within the page content type itself (when available).

Image Alt Text Video Tutorial

Link names

Links must describe their destination. Avoid generic phrases:

  • "Click here"
  • "Read more"
  • "Link"

Instead, use specific language:

  • "Download the Finance PDF"
  • "View the Academic Calendar"
  • "Contact the Office of Admission"

If you saw the link language out of context, would you know where it goes? If not, rewrite it.

Page titles

Page titles appear in the tab of your browser. Each page must have a unique, descriptive title. The page title should:

  • reflect the content of the page.
  • match or closely align with the main heading.
  • not be generic (e.g. "home" or "untitled").

In Terminalfour, add this in the "Meta Title" field under the "General" tab and save the page. 

Page Title Video Tutorial

Tables

Tables must include header rows (and header columns when appropriate). Without headers, assistive technology cannot interpret the structure of the table. Use tables only for data, not for layout.

Column 1 Column 2
table data table date
example example
Column 1 Column 2 Column 3
Row 1 table data table data
Row 2 example example

Headings

Headings create structure and help users navigate. Follow this hierarchy:

  • One Level 1 heading per page
  • Level 2 headings for main sections
  • Level 3 headings for sub-sections

Do not change text size or bold text to simulate a heading. Use the proper heading styles in T4.

When to ask for help

You should contact the UMC Digital Team if:

  • you are unsure how to structure complex content.
  • your page is flagged repeatedly for accessibility issues.
  • you are uploading a PDF.
  • you receive accessibility-related feedback.

Accessibility is a shared responsibility. Asking early prevents rework later.

If you would like a detailed accessibility report from our Siteimprove platform to identify specific areas for improvement, please submit a request.

Why accessibility matters

Loyola is working to meet updated ADA Title III web accessibility requirements, which adopt WCAG 2.1 Level AA standards. This means all web content must meet established accessibility criteria. Accessibility ensures:

  • everyone can access important information.
  • Loyola meets legal and ethical obligations.
  • content is usable across devices and technologies.

What is WCAG?

The Web Content Accessibility Guidelines (WCAG) are internationally recognized standards for digital accessibility. WCAG is based on four principles:

  • Perceivable Content can be seen or heard
  • Operable Users can navigate and interact
  • Understandable Content is clear and predictable
  • Robust Works with assistive technologies

You are not expected to memorize WCAG criteria. UMC Digital monitors and supports compliance at the system level.

Additional Resources